Announcement

Collapse
No announcement yet.

Avi`s that are made with huffyuv codec impossible to edit!!! :(

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Avi`s that are made with huffyuv codec impossible to edit!!! :(

    I have tried the lossless huffyv codec and the quality is really good. Didnt actually thought it was that lossless
    btw, when i open the file in adobe premiere everythings works find, but when i drag it into the target monitor after editing, adobe gives a failure and closes. anyone knows what todo?

    this is the failure
    " this program has performed an illegal operation and will be shut down.

    if the problem persists, contact the program vendor.

  • #2
    Did you select it as the target compression in the Premiere setups? It edits fine here using a Matrox Marvel G400, VideoTools 1.52 and Premiere 5.1c.

    Dr. Mordrid

    Comment


    • #3
      Dr mordrid: what option do you use when capturing with huffyuv? you use yuv2 or rgb?
      and can you tell me your exact settings in the huffyuv?

      i have tried both the compressions,the one called matrox yuv2 and the other huffyuv
      (ill guess it is when i open a new project and in the video settings / compression) ill choose it?

      but what programs do you use when capturing huffyuv to?
      i captured with virtualdub.
      but maybe i do something wrong when capturing it

      Comment


      • #4
        The Author has already posted version 2.1, which I believe addresses this issue. I didn't look to close, as I don't use premier. You might check his site and see what's up. http://www.math.berkeley.edu/~benrg/huffyuv.html

        Comment


        • #5
          I choose the YUY2 capture mode & rez of choice and then select HuffYUV from the Compression list. As Prospero says the 2.1 update is much enhanced.

          Dr. Mordrid


          [This message has been edited by Dr Mordrid (edited 21 July 2000).]

          Comment


          • #6
            Dr mordrid and Prospero
            It was with those latest drivers i did try, version 2.1 (with version 1.3.1 it seems find with none errors) so maybe i have found the furst bug or anything)

            Comment

            Working...
            X